From 97b442f5fa8cbed30d020d719bca8f61566fdf1a Mon Sep 17 00:00:00 2001 From: robertl Date: Wed, 7 Jun 2006 20:13:51 +0000 Subject: [PATCH] Sketch in Magellan format notes. (Still more to do...) --- xmldoc/formats/magellan.xml | 51 +++++++++++++----- xmldoc/formats/magellan1.xml | 54 +++++++++++++++----- xmldoc/formats/magellanx.xml | 21 +++++--- xmldoc/formats/options/magellan-maxcmts.xml | 14 ++++- xmldoc/formats/options/magellan1-baud.xml | 9 +++- xmldoc/formats/options/magellan1-deficon.xml | 16 +++++- xmldoc/formats/options/magellan1-maxcmts.xml | 14 ++++- xmldoc/formats/options/magellan1-noack.xml | 18 ++++++- xmldoc/formats/options/magellan1-nukewpt.xml | 11 +++- xmldoc/formats/options/magellanx-maxcmts.xml | 14 ++++- 10 files changed, 179 insertions(+), 43 deletions(-) diff --git a/xmldoc/formats/magellan.xml b/xmldoc/formats/magellan.xml index ef850831f..bc671532e 100644 --- a/xmldoc/formats/magellan.xml +++ b/xmldoc/formats/magellan.xml @@ -1,14 +1,37 @@ - - - - Waypoint serial upload and download works reliably to the -315, 330, Meridian, and SportTrak family. I expect it to work on any -modern Magellan unit. - As of 08/30/02, GPSBabel can also read and write the -files that can be stuck on the SD memory cards with the Meridian -models. Simply specify a file instead of a serial port. - Communication errors are handled robustly and -verification of data is enabled. - Additional suboptions: baud: may be 1200, 2400, 4800, 9600, -19200, but must match receiver. - +GPSBabel supports the following Magellan receivers: + + 310 + 315 + Map330 + SporTrak Map Color + SporTrak Map + SporTrak Map Pro + SporTrak Map Topo + Meridian (green or yellow) + Meridian Gold + Meridian Platinum + Meridian Color + Explorist 100 (with aftermarket cable) + Explorist 200 (with aftermarket cable) + Explorist 300 (with aftermarket cable) + Explorist 210 + Explorist 300 + Explorist 400 + Explorist 500 + Explorist 600 + Explorist XL + + + + + This format is used for both the serial protocol used on the + devices with serial ports such as Map330 and Meridian and for + the files stored either in either the unit's internal memory + (Explorist 210, 400, 500, 600, XL) or on removable memory. + + + If you specify a serial port for the file (.e.g. "COM1", "/dev/ttyS0") + to be read or written, GPSBabel will use serial protocol. Specifying + a file, either on local filesystem or on a mounted flash card reader, + will results in the file-based format being used. + diff --git a/xmldoc/formats/magellan1.xml b/xmldoc/formats/magellan1.xml index ef850831f..2ee5fbf23 100644 --- a/xmldoc/formats/magellan1.xml +++ b/xmldoc/formats/magellan1.xml @@ -1,14 +1,40 @@ - - - - Waypoint serial upload and download works reliably to the -315, 330, Meridian, and SportTrak family. I expect it to work on any -modern Magellan unit. - As of 08/30/02, GPSBabel can also read and write the -files that can be stuck on the SD memory cards with the Meridian -models. Simply specify a file instead of a serial port. - Communication errors are handled robustly and -verification of data is enabled. - Additional suboptions: baud: may be 1200, 2400, 4800, 9600, -19200, but must match receiver. - +GPSBabel supports the following Magellan receivers: + + 310 + 315 + Map330 + SporTrak Map Color + SporTrak Map + SporTrak Map Pro + SporTrak Map Topo + Meridian (green or yellow) + Meridian Gold + Meridian Platinum + Meridian Color + Explorist 100 (with aftermarket cable) + Explorist 200 (with aftermarket cable) + Explorist 300 (with aftermarket cable) + Explorist 210 + Explorist 300 + Explorist 400 + Explorist 500 + Explorist 600 + Explorist XL + + + +The RoadMate family of products is not supported. + + + + This format is used for both the serial protocol used on the + devices with serial ports such as Map330 and Meridian and for + the files stored either in either the unit's internal memory + (Explorist 210, 400, 500, 600, XL) or on removable memory. + + + If you specify a serial port for the file (.e.g. "COM1", "/dev/ttyS0") + to be read or written, GPSBabel will use serial protocol. Specifying + a file, either on local filesystem or on a mounted flash card reader, + will results in the file-based format being used. + diff --git a/xmldoc/formats/magellanx.xml b/xmldoc/formats/magellanx.xml index 707df3b32..be4fa14a9 100644 --- a/xmldoc/formats/magellanx.xml +++ b/xmldoc/formats/magellanx.xml @@ -1,9 +1,14 @@ - - - - The SD card format used by the Magellan Explorist 400, -500, and 600. It's identical to the Magellan SD format used by -Meridian, but allows longer waypoint names. - You should name any file created with this format with a -".upt" extension so the firmware can read it. + + This is the SD card format used by the Magellan Explorist 400, + 500, 600, and XL and internally on those devices plus the + Explorist 210. Waypoints are identical to the Magellan SD format + used by Meridian, but allows longer waypoint names. Routes are + subtly different. + + + You should name any file containing waypoints created with + this format with a ".upt" extension so the firmware can read it. + Similarly, routes should be named ".rte" and tracks should be + named ".log". + diff --git a/xmldoc/formats/options/magellan-maxcmts.xml b/xmldoc/formats/options/magellan-maxcmts.xml index 8b1378917..1c46dd108 100644 --- a/xmldoc/formats/options/magellan-maxcmts.xml +++ b/xmldoc/formats/options/magellan-maxcmts.xml @@ -1 +1,13 @@ - + +The maxcmts option allows you to specify the number comments that will +be sent to the unit. + + +Magellan receivers allow a maximum of 200 waypoint comments. Unfortunately, +DirectRoute uses waypoint comments to provide next turn directions for +navigation pop-ups and that comes from that pool of 200 comments. It +is therefore sometimes convenient to limit the number of waypoint +comments written to the receiver. For example, a geocacher might want +to upload 400 waypoints, but only 190 with comments so that DirectRoute +could provide driving directions for the next ten turns. + diff --git a/xmldoc/formats/options/magellan1-baud.xml b/xmldoc/formats/options/magellan1-baud.xml index 8b1378917..0682faa0a 100644 --- a/xmldoc/formats/options/magellan1-baud.xml +++ b/xmldoc/formats/options/magellan1-baud.xml @@ -1 +1,8 @@ - + + This option causes GPSBabel to use the given baud rate for serial + communications. It must match the given baud rate on the receiver. The + default value matches the default on the receiver, 4800. + + + Valid options are 1200, 2400, 4800, 9600, 19200, 57600, and 115200. + diff --git a/xmldoc/formats/options/magellan1-deficon.xml b/xmldoc/formats/options/magellan1-deficon.xml index 8b1378917..f1d272b05 100644 --- a/xmldoc/formats/options/magellan1-deficon.xml +++ b/xmldoc/formats/options/magellan1-deficon.xml @@ -1 +1,15 @@ - + +This option specifies the icon or waypoint type to write for each waypoint on +output. + + +If this option is specified, its value will be used for all waypoints, not +just those that do not already have descriptions. That is, this option +overrides any icon description that might be in the input file. + + + +This option has no effect on input. + diff --git a/xmldoc/formats/options/magellan1-maxcmts.xml b/xmldoc/formats/options/magellan1-maxcmts.xml index 8b1378917..1c46dd108 100644 --- a/xmldoc/formats/options/magellan1-maxcmts.xml +++ b/xmldoc/formats/options/magellan1-maxcmts.xml @@ -1 +1,13 @@ - + +The maxcmts option allows you to specify the number comments that will +be sent to the unit. + + +Magellan receivers allow a maximum of 200 waypoint comments. Unfortunately, +DirectRoute uses waypoint comments to provide next turn directions for +navigation pop-ups and that comes from that pool of 200 comments. It +is therefore sometimes convenient to limit the number of waypoint +comments written to the receiver. For example, a geocacher might want +to upload 400 waypoints, but only 190 with comments so that DirectRoute +could provide driving directions for the next ten turns. + diff --git a/xmldoc/formats/options/magellan1-noack.xml b/xmldoc/formats/options/magellan1-noack.xml index 8b1378917..f8d84cab2 100644 --- a/xmldoc/formats/options/magellan1-noack.xml +++ b/xmldoc/formats/options/magellan1-noack.xml @@ -1 +1,17 @@ - + +Magellan's protocol specification strongly encourages the use of software +acknowledgements on every packets. This is a simple "this is what I think +I heard. If you agree that I heard it correctly, let's go to the next packet" +handshake that is used to ensure the integrity of the data transfer. + + +Certain firmware versions have problems handling this which makes transfers +unnecessarily slow. Transfers on all units at high serial speeds are also +severely restricted by this process. + + +In controlled environments (good cables, low electrical noise, receiving +from the unit, not doing donuts with the unit set to "track up" at a 150 +mile scale with 500 waypoints on the screen) it is sometimes useful to +release that safety belt by using the "noack" suboption. + diff --git a/xmldoc/formats/options/magellan1-nukewpt.xml b/xmldoc/formats/options/magellan1-nukewpt.xml index 8b1378917..5ca891611 100644 --- a/xmldoc/formats/options/magellan1-nukewpt.xml +++ b/xmldoc/formats/options/magellan1-nukewpt.xml @@ -1 +1,10 @@ - + +This option erases all waypoints in the receiver before doing a transfer. + + +This is a convenient option to use in automated processes where you want +to ensure the units starts with a clean state before sending waypoints to +it. Using this option on transmit is a better idea than doing it on +receive since the latter would erase all the waypoints before asking the +unit to send all the waypoints. + diff --git a/xmldoc/formats/options/magellanx-maxcmts.xml b/xmldoc/formats/options/magellanx-maxcmts.xml index 8b1378917..1c46dd108 100644 --- a/xmldoc/formats/options/magellanx-maxcmts.xml +++ b/xmldoc/formats/options/magellanx-maxcmts.xml @@ -1 +1,13 @@ - + +The maxcmts option allows you to specify the number comments that will +be sent to the unit. + + +Magellan receivers allow a maximum of 200 waypoint comments. Unfortunately, +DirectRoute uses waypoint comments to provide next turn directions for +navigation pop-ups and that comes from that pool of 200 comments. It +is therefore sometimes convenient to limit the number of waypoint +comments written to the receiver. For example, a geocacher might want +to upload 400 waypoints, but only 190 with comments so that DirectRoute +could provide driving directions for the next ten turns. + -- 2.30.2